Origin: upstream, commit: 8f535370b9efbc91673b20c6987a5cae4f6dc562 Added-by: Rob Browning <rlb@defaultvalue.org>
Bug: https://debbugs.gnu.org/80851
Bug-Debian: https://bugs.debian.org/1134692
README-Debian: An SVG-related security vulnerability has been fixed (CVE-2026-6861)
This vulnerability, a memory corruption issue, could occur when Emacs
processed specially crafted SVG (Scalable Vector Graphics)
CSS (Cascading Style Sheets) data. A local user could exploit this by
convincing a victim to open a malicious SVG file, which might lead to a
denial of service (DoS) or potentially information disclosure.
Gbp-Pq: Name 0023-src-image.c-svg_load_image-Fix-off-by-one-mistake-bu.patch
Sean Whitton [Wed, 26 Feb 2025 08:13:44 +0000 (16:13 +0800)]
Disable server-tests/server-force-stop/keeps-frames on riscv64
This test often hangs on the Debian buildds.
It simply fails on a porterbox, at least for the emacs-nox phase
of the build, though seemingly not the emacs-lucid phase.
Gbp-Pq: Name 0020-Disable-server-tests-server-force-stop-keeps-frames-.patch
Sean Whitton [Tue, 15 Nov 2022 23:26:59 +0000 (16:26 -0700)]
Mark flaky test process-tests/multiple-threads-waiting as unstable
It times out:
passed 22/28 process-tests/fd-setsize-no-crash/make-serial-process (0.021449 sec)
make[5]: *** [Makefile:182: src/process-tests.log] Error 134
GEN src/regex-emacs-tests.log
GEN src/search-tests.log
GEN src/syntax-tests.log
GEN src/textprop-tests.log
GEN src/thread-tests.log
GEN src/timefns-tests.log
GEN src/undo-tests.log
GEN src/xdisp-tests.log
GEN src/xfaces-tests.log
GEN src/xml-tests.log
make[5]: Leaving directory '/<<PKGBUILDDIR>>/debian/build-gtk/test'
make[4]: [Makefile:335: check-doit] Error 2 (ignored)
SUMMARY OF TEST RESULTS
-----------------------
Files examined: 375
Ran 5408 tests, 28 failed to run, 5273 results as expected, 0 unexpected, 135 skipped
1 files did not finish:
src/process-tests.log
make[4]: *** [Makefile:336: check-doit] Error 2
Gbp-Pq: Name 0011-Mark-flaky-test-process-tests-multiple-threads-waiti.patch
Rob Browning [Sun, 16 Dec 2018 23:13:36 +0000 (17:13 -0600)]
Mark vc-bzr-test-fauilt-bzr-autoloads as unstable for now
Currently the test fails like this:
Running 3 tests (2018-12-17 12:17:43-0600)
passed 1/3 vc-bzr-test-bug9726
Mark set
Press C-c C-c when you are done editing.
Enter a change comment. Type C-c C-c when done
passed 2/3 vc-bzr-test-bug9781
Falling back on "slow" status detection ((file-missing "Opening input file" "No such file or directory" "/tmp/vc-bzr-testVlgmsb/bzr/.bzr/checkout/dirstate"))
Error: (error "Running bzr status --no-classify loaddefs.el...FAILED (status 3)")
Warnings in `bzr' output: bzr: ERROR: invalid header line: ''
Error: (error "Running bzr status --no-classify loaddefs.el...FAILED (status 3)")
Warnings in `bzr' output: bzr: ERROR: invalid header line: ''
Rob Browning [Mon, 10 Oct 2016 22:35:56 +0000 (17:35 -0500)]
Kill gpg agent in package-test.el to avoid a race
package-test.el should no longer fail during clean up.
* Previously a delete-directories call raced with the gpg agent's own
cleanup process (presumably triggered by the first deletion of one of
the agent's sockets). As a result, it looks like the agent might
delete one of its sockets after delete-directories had decided to
delete the socket, but before it made the attempt, causing an
exception.
* To fix the problem, explicitly ask gpg-connect-agent to kill the agent
before attempting to delete the gnupg home directory, and then delete
via "rm -rf" to ignore any vanishing files.
Gbp-Pq: Name 0007-Kill-gpg-agent-in-package-test.el-to-avoid-a-race.patch
Rob Browning [Tue, 5 Apr 2011 03:46:28 +0000 (22:46 -0500)]
Modify the output of (version) to indicate Debian modifications
The output of (version) has been modified to indicate Debian modifications.
Author: Rob Browning <rlb@defaultvalue.org> Added-by: Rob Browning <rlb@defaultvalue.org>
Gbp-Pq: Name 0005-Modify-the-output-of-version-to-indicate-Debian-modi.patch
Rob Browning [Tue, 5 Apr 2011 03:46:24 +0000 (22:46 -0500)]
Remove files that appear to be incompatible with the DFSG
Files that appear to be incompatible with the DFSG have been removed.
A number of files have been removed from this package because their
licenses are not compatible with the Debian Free Software Guidelines
(DFSG), or because it wasn't completely clear that their licenses are
compatible.
In particular, all of the files which are covered under the GFDL and
have invariant sections have been removed in accordance with this
General Resolution: http://www.debian.org/vote/2006/vote_001.
The files that have been removed, but still appear to be
distributable, have been moved to packages in Debian's non-free
section.
Author: Rob Browning <rlb@defaultvalue.org> Added-by: Rob Browning <rlb@defaultvalue.org>
Status: new
Gbp-Pq: Name 0003-Remove-files-that-appear-to-be-incompatible-with-the.patch
* Mark esh-proc-test/kill-pipeline as unstable for now. Skip it since
it fails sporadically on at least s390x. Add
0024-Mark-esh-proc-test-kill-pipeline-as-unstable-for-now.patch to
address the issue.
* Fix an SVG-related vulnerability (CVE-2026-6861). Add
0025-src-image.c-svg_load_image-Fix-off-by-one-mistake-bu.patch which
includes the upstream patch to fix the problem. Thanks to Salvatore
Bonaccorso for reporting the issue. (Closes: 1134692)
* Don't run bytecomp-tests--dest-mountpoint where bwrap doesn't work.
Add 0026-bytecomp-tests-dest-mountpoint-only-run-test-if-bwra.patch to
address the issue. Thanks to Santiago Vila for reporting the
issue. (Closes: 1129189)
* Skip two more proced-tests in debian that are skipped on darwin to
avoid hanging during the tests. Add
0025-Skip-some-proced-tests-that-appear-to-be-hanging.patch to address
the issue.
* Mitigate a risk of executing arbitrary code when opening a file. The
vulnerability that has been mitigated could allow a specially crafted
file to trigger execution of arbitrary Emacs Lisp code immediately
upon visiting it in Emacs. The broader issue is described here:
https://debbugs.gnu.org/80574
Add 0030-Mitigate-arbitrary-code-execution-vulnerability.patch to
include the upstream patch addressing the problem. Thanks to Nicholas
D Steeves for reporting the issue.
projects / emacs.git / log